valueflows

valueflows docs
git clone https://s.sonu.ch/~srfsh/valueflows.git
Log | Files | Refs | README

2016-01-03 minutes (3500B)


      1 
      2 Agenda:
      3 
      4 1. How to work with separate repos when we need to refer to things already created in another repo (in json-ld or turtle/VOWL work)?
      5 
      6 2. Related possibly, how to keep our work in turtle and json-ld in sync?
      7 
      8 3. What can we nail down on Agent so that people like Connor can use it soon?
      9 
     10 4. Tracking our economic activities, staring with time we work on github issues. Demo of prototype we currently develop in Munich during hackathon hosted by [CO-OPEN](https://github.com/CO-OPEN).
     11 
     12 5. New issue for each meeting. To have a reference when we track time that we work on writing agenda, participaing in meeting, taking care for minutes etc.
     13 
     14 6. Dependency graph for tasks/issues/goals and linking it to dependencies (needs) of people who offer contributing to them. Interesting proprietary webapp to visualize dependencies on tasks - https://casual.pm/
     15 
     16     * Map tasks/issues/goals to VF vocab
     17     * Track in contribution activities (sub processes?) resources used in that process / during that activity, eg. coding - computer, internet connection, physical workspace, electricity etc.
     18 
     19 7. Bridging work with https://www.w3.org/community/economy/
     20 
     21 8. Quick chat about https://ipfs.io ?
     22 
     23 
     24 Chat from the online meeting
     25 
     26 me
     27 2:12 PM
     28 demo:
     29 (I'll try to take notes)
     30 browseer, initialized with id about self
     31 browse other related resources
     32 goals: github issues
     33 click on issue: track time on it
     34 activities
     35 will have types of activities
     36 activity is a chunk of work
     37 relate to the issue
     38 posts to container anywhere on the web when record activity
     39 container referenced by agent (uri id)
     40 resources:
     41 web resources
     42 (not economic resource)
     43 project:
     44 software
     45 different meanings to "project"
     46 goal, end date vs ongoing more organizational
     47 >> second definition to samuel
     48 more like a group of people
     49 can nest projects and goals as deep as you want
     50 github repo = project right now
     51 -so less of an organization using github right now
     52 (elf)
     53 notice focus on top
     54 left: filters by type of other related entities
     55 right side, relationship types (sort of)
     56 --later, samual, curated list of projects etc., not just related to the person authenticated
     57 personal entry point or portal with curation
     58 like open source projects or cooking or whatever
     59 .
     60 .
     61 where is it at?
     62 when can we try it?
     63 web access more and more liberal as to data published
     64 .
     65 soon as long as people wiling to file bug reports
     66 we are good being testers
     67 want it to consume data from multiple sources
     68 maybe next couple weeks
     69 .
     70 other ways to infer from github data
     71 git to prov?
     72 .
     73 mikey: will model the contracting he is doing, and others from craftworks
     74 Michael Williams
     75 2:41 PM
     76 https://gist.github.com/ahdinosaur/2c4f7f714c75f824d8e1
     77 me
     78 2:42 PM
     79 (from colab example)
     80 .
     81 samuel: track the time and value flows on building this app
     82 long term, using as curated list
     83 of open source projects of any kind
     84 and their relations to each other
     85 works in movie industry as camera assistance, see potential to adapt there, open source principles
     86 do a music video
     87 publish as open source project and map dependencies on contributions
     88 .
     89 and are other people who might be itnerested
     90 .
     91 would like to keep it tight in the beginning
     92 feedback loops
     93 .
     94 movie:maybe value equation later
     95 .
     96 elf selfdogfood: more systematic on bus trips etc. that he does
     97 publish everyday his activities
     98 contributions
     99 link dependencies
    100 also equipment, etc.
    101 for example uses computer to contribution, and when it breaks, people can contribute to that
    102 people need to cover contributors
    103 .
    104 meet again in 2 weeks